[Docs] Document destructive command guard approvals - #20
Draft
zoomote[bot] wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Documents the Destructive Command Guard setting in the Auto-Approving Actions guide, including the Execute-permission prerequisite, automatic allows, blocked-command decisions, command-list precedence, and installation failures.
Why this change was made
The DCG command-approval behavior is user-facing and needs clear setup and safety guidance alongside the extension changes.
Impact
Users can understand when DCG runs commands automatically and when Zoo requires a one-time decision.
Related PRs
Screenshots